Notes/Domino Fix List
 |  |
| SPR # CLEC43UL2C | Fixed in 5.0.7 release |  |
Product Area: Server; Designer Technical Area: Server - Updall - Indexing (Views) Platform: OS/2; Win NT
SPR# CLEC43UL2C - Fixed a problem where the Design Collection was reloaded twice.
Technote Number: 1086041
Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Notes 4.6.4a and Notes 4.6.5 and 4.5.7g. It has also been addressed in Notes
5.0.7. However, the issue still occurs in Notes 4.5x Client on the OS/2
platform.
Excerpt from the Lotus Notes and Lotus Domino Release 4.6.4a and 4.5.7g QMU,
and 4.6.5 QMR fix lists:
SPR# CLEC43UL2C - Fix a performance problem resulting from a workstation
reloading the design collection of a database each time a view or folder was
opened for the first time. Obviously, this performance problem would be greatly
amplified on slow connections.
Excerpt from the Lotus Notes and Domino Release 5.0.7 QMR fix list (available
at http://www.notes.net):
Server - Updall - Indexing (Views)
SPR# CLEC43UL2C - Fixed a problem where the Design Collection was reloaded
twice.
In releases of Notes prior to 4.6.4a and 4.6.5, a problem had been discovered
that caused design elements to be re-cached if a new collection was built in
the database. A collection is the physical index of documents associated with
a view or folder. The building of a new collection updates an internal time
stamp, that forces design elements to get re-cached to the CACHE.DSK, even
though the design elements are current and have not been updated.
For example, a user may have the latest design elements cached locally. This
user typically may work in the Inbox, but decides to click on the "All
Documents" view, which has never been opened before. Since it has never been
opened before, this forces the building of a new collection. The building of a
new collection updates the internal time stamp that Notes uses to determine
when to refresh cached design elements. The next time the user closes and
re-opens their mail file, the design elements will be purged from the CACHE.DSK
and re-cached from the database on the server.
Over a LAN, the delay is minimal and typically would not be noticed, but over a
slow dial-up line, the delay can be more significant.Supporting Information:
Design elements (forms, subforms, navigators, scripts, etc.) for a database are
cached locally in the CACHE.DSK. This speeds up access to commonly used design
elements. When a database is opened, we do a check to see if the design
elements need to be re-cached from the database, based on an internal time
stamp.
Related Documents:
More >
Last Modified on 05/15/2001
Go back
|